Event-driven provisioning of new edge servers in 5g media streaming architecture

ABSTRACT

A method for event-driven provisioning of edge servers in a 5G Media Streaming (5GMS) architecture, including setting, by a 5GMS AP, during provisioning or updating of a first EAS one or more event trigger conditions and determining, by a 5GMS AF at the first EAS, based on an indicator event associated with the first EAS, that at least one of the one or more event trigger conditions of the first EAS is satisfied. Generating, by the 5GMS AP, a trigger event in response and setting, by the 5GMS AP, during the provisioning or updating of a second EAS, one or more activating conditions for activating the second EAS. The 5GMS AP determining that the generated trigger event is associated with at least one of the activating conditions for activating the second EAS; and transmitting a message causing activation of the second EAS.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a Continuation application of U.S. application Ser.No. 18/080,195, filed Dec. 13, 2022, which claims priority from U.S.Provisional Application No. 63/307,546, filed on Feb. 7, 2022, in theUnited States Patent and Trademark Office, the disclosure of which isincorporated herein by reference in its entirety.

FIELD

The disclosure generally relates to 5th generation (5G) media streaming(5GMS), and, in particular, to provisioning new edge application serversbased on set events.

BACKGROUND

The 3^(rd) Generation Partnership Project (3GPP) recently provided anextension to use the edge servers in 5G media streaming (5GMS)architecture. However, the detailed methods of provisioning these edgeservers are not defined yet.

The 3^(rd) Generation Partnership Project (3GPP) TS23.558 defines thegeneral architecture for enabling edge application, including thediscovery of hardware capabilities of an edge element and the discoveryof the edge application by Application clients. 3GPP TS 26.501 definesthe general architecture for 5G media streaming applications. Itrecently added the use of TS23.558 edge architecture as part of the5GMSA architecture as an extension.

However, the actual method of provisioning such services is not defined.This disclosure defines a provisioning method of new edge servers basedon the triggering events of the running edge servers.

SUMMARY

According to one or more embodiments, a method for event-drivenprovisioning of edge servers in a 5G Media Streaming (5GMS) architecturemay be provided. The method may be executed by at least one processor,and may include, setting, by a 5GMS application provider (AP), duringprovisioning or updating of a first edge application server (EAS), oneor more event trigger conditions; determining, by a 5GMS ApplicationFunction (AF) at the first EAS, based on an indicator event associatedwith the first EAS, that at least one of the one or more event triggerconditions of the first EAS is satisfied; generating, by the 5GMS AP, atrigger event in response to determining that the at least one of theevent trigger conditions of the first EAS is satisfied; setting, by the5GMS AP, during the provisioning or updating of a second EAS, one ormore activating conditions for activating the second EAS; determining,by the 5GMS AP, that the generated trigger event is associated with atleast one of the one or more activating conditions for activating thesecond EAS; and transmitting a message associated with the generatedtrigger event to EASs in the 5GMS architecture, the message causingactivation of the second EAS.

According to one or more embodiments, a device for event-drivenprovisioning of edge servers in a 5G Media Streaming (5GMS) architecturemay be provided. The device may include at least one memory configuredto store program code; and at least one processor configured to read theprogram code and operate as instructed by the program code. The programcode may include, first setting code configured to cause the at leastone processor to set, by a 5GMS application provider (AP), duringprovisioning or updating of a first edge application server (EAS), oneor more event trigger conditions; first determining code configured tocause the at least one processor to determine, by a 5GMS ApplicationFunction (AF) at the first EAS, based on an indicator event associatedwith the first EAS, that at least one of the one or more event triggerconditions of the first EAS is satisfied; generating code configured tocause the at least one processor to generate, by the 5GMS AP, a triggerevent in response to determining that the at least one of the eventtrigger conditions of the first EAS is satisfied; second setting codeconfigured to cause the at least one processor to set, by the 5GMS AP,during the provisioning or updating of a second EAS, one or moreactivating conditions for activating the second EAS; second determiningcode configured to cause the at least one processor to determine, by the5GMS AP, that the generated trigger event is associated with at leastone of the one or more activating conditions for activating the secondEAS; transmitting code configured to cause the at least one processor totransmit a message associated with the generated trigger event to EASsin the 5GMS architecture, the message causing activation of the secondEAS.

According to one or more embodiments, a non-transitory computer-readablemedium stores instructions may be provided. The instructions may includeone or more instructions that, when executed by one or more processorsof a device for event-driven provisioning of edge servers in a 5G MediaStreaming (5GMS) architecture, cause the one or more processors to set,by a 5GMS application provider (AP), during provisioning or updating ofa first edge application server (EAS), one or more event triggerconditions; determine, by a 5GMS Application Function (AF) at the firstEAS, based on an indicator event associated with the first EAS, that atleast one of the one or more event trigger conditions of the first EASis satisfied; generate, by the 5GMS AP, a trigger event in response todetermining that the at least one of the event trigger conditions of thefirst EAS is satisfied; set, by the 5GMS AP, during the provisioning orupdating of a second EAS, one or more activating conditions foractivating the second EAS; determine, by the 5GMS AP, that the generatedtrigger event is associated with at least one of the one or moreactivating conditions for activating the second EAS; and transmit amessage associated with the generated trigger event to EASs in the 5GMSarchitecture, the message causing activation of the second EAS.

BRIEF DESCRIPTION OF THE DRAWINGS

Further features, the nature, and various advantages of the disclosedsubject matter will be more apparent from the following detaileddescription and the accompanying drawings in which:

FIG. 1 is a diagram of an environment in which methods, apparatuses, andsystems described herein may be implemented, according to embodiments.

FIG. 1 .

FIG. 2 is a block diagram of example components of one or more devicesof FIG. 3 is a block diagram of a media architecture for mediastreaming, according to embodiments.

FIG. 4 is a diagram of a 5^(th) generation (5G) edge networkarchitecture, according to embodiments.

FIG. 5 is a diagram of a 5G media streaming architecture for enablingedge applications, according to embodiments.

FIG. 6 is a flowchart of an example process for event-drivenprovisioning of edge servers in a media-streaming network.

DETAILED DESCRIPTION

FIG. 1 is a diagram of an environment 100 in which methods, apparatuses,and systems described herein may be implemented, according toembodiments. As shown in FIG. 1 , the environment 100 may include a userdevice 110, a platform 120, and a network 130. Devices of theenvironment 100 may interconnect via wired connections, wirelessconnections, or a combination of wired and wireless connections.

The user device 110 includes one or more devices capable of receiving,generating, storing, processing, and/or providing information associatedwith platform 120. For example, the user device 110 may include acomputing device (e.g., a desktop computer, a laptop computer, a tabletcomputer, a handheld computer, a smart speaker, a server, etc.), amobile phone (e.g., a smart phone, a radiotelephone, etc.), a wearabledevice (e.g., a pair of smart glasses or a smart watch), or a similardevice. In some implementations, the user device 110 may receiveinformation from and/or transmit information to the platform 120.

The platform 120 includes one or more devices as described elsewhereherein. In some implementations, the platform 120 may include a cloudserver or a group of cloud servers. In some implementations, theplatform 120 may be designed to be modular such that software componentsmay be swapped in or out depending on a particular need. As such, theplatform 120 may be easily and/or quickly reconfigured for differentuses.

In some implementations, as shown, the platform 120 may be hosted in acloud computing environment 122. Notably, while implementationsdescribed herein describe the platform 120 as being hosted in the cloudcomputing environment 122, in some implementations, the platform 120 maynot be cloud-based (i.e., may be implemented outside of a cloudcomputing environment) or may be partially cloud-based.

The cloud computing environment 122 includes an environment that hoststhe platform 120. The cloud computing environment 122 may providecomputation, software, data access, storage, etc. services that do notrequire end-user (e.g., the user device 110) knowledge of a physicallocation and configuration of system(s) and/or device(s) that hosts theplatform 120. As shown, the cloud computing environment 122 may includea group of computing resources 124 (referred to collectively as“computing resources 124” and individually as “computing resource 124”).

The computing resource 124 includes one or more personal computers,workstation computers, server devices, or other types of computationand/or communication devices. In some implementations, the computingresource 124 may host the platform 120. The cloud resources may includecompute instances executing in the computing resource 124, storagedevices provided in the computing resource 124, data transfer devicesprovided by the computing resource 124, etc. In some implementations,the computing resource 124 may communicate with other computingresources 124 via wired connections, wireless connections, or acombination of wired and wireless connections.

As further shown in FIG. 1 , the computing resource 124 includes a groupof cloud resources, such as one or more applications (APPs) 124-1, oneor more virtual machines (VMs) 124-2, virtualized storage (VSs) 124-3,one or more hypervisors (HYPs) 124-4, or the like.

The application 124-1 includes one or more software applications thatmay be provided to or accessed by the user device 110 and/or theplatform 120. The application 124-1 may eliminate a need to install andexecute the software applications on the user device 110. For example,the application 124-1 may include software associated with the platform120 and/or any other software capable of being provided via the cloudcomputing environment 122. In some implementations, one application124-1 may send/receive information to/from one or more otherapplications 124-1, via the virtual machine 124-2.

The virtual machine 124-2 includes a software implementation of amachine (e.g. a computer) that executes programs like a physicalmachine. The virtual machine 124-2 may be either a system virtualmachine or a process virtual machine, depending upon use and degree ofcorrespondence to any real machine by the virtual machine 124-2. Asystem virtual machine may provide a complete system platform thatsupports execution of a complete operating system (OS). A processvirtual machine may execute a single program, and may support a singleprocess. In some implementations, the virtual machine 124-2 may executeon behalf of a user (e.g., the user device 110), and may manageinfrastructure of the cloud computing environment 122, such as datamanagement, synchronization, or long-duration data transfers.

The virtualized storage 124-3 includes one or more storage systemsand/or one or more devices that use virtualization techniques within thestorage systems or devices of the computing resource 124. In someimplementations, within the context of a storage system, types ofvirtualizations may include block virtualization and filevirtualization. Block virtualization may refer to abstraction (orseparation) of logical storage from physical storage so that the storagesystem may be accessed without regard to physical storage orheterogeneous structure. The separation may permit administrators of thestorage system flexibility in how the administrators manage storage forend users. File virtualization may eliminate dependencies between dataaccessed at a file level and a location where files are physicallystored. This may enable optimization of storage use, serverconsolidation, and/or performance of non-disruptive file migrations.

The hypervisor 124-4 may provide hardware virtualization techniques thatallow multiple operating systems (e.g., “guest operating systems”) toexecute concurrently on a host computer, such as the computing resource124. The hypervisor 124-4 may present a virtual operating platform tothe guest operating systems, and may manage the execution of the guestoperating systems. Multiple instances of a variety of operating systemsmay share virtualized hardware resources.

The network 130 includes one or more wired and/or wireless networks. Forexample, the network 130 may include a cellular network (e.g. a fifthgeneration (5G) network, a long-term evolution (LTE) network, a thirdgeneration (3G) network, a code division multiple access (CDMA) network,etc.), a public land mobile network (PLMN), a local area network (LAN),a wide area network (WAN), a metropolitan area network (MAN), atelephone network (e.g. the Public Switched Telephone Network (PSTN)), aprivate network, an ad hoc network, an intranet, the Internet, a fiberoptic-based network, or the like, and/or a combination of these or othertypes of networks.

The number and arrangement of devices and networks shown in FIG. 1 areprovided as an example. In practice, there may be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 1 . Furthermore, two or more devices shown in FIG. 1 maybe implemented within a single device, or a single device shown in FIG.1 may be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g. one or more devices) of theenvironment 100 may perform one or more functions described as beingperformed by another set of devices of the environment 100.

FIG. 2 is a block diagram of example components of one or more devicesof FIG. 1 . The device 200 may correspond to the user device 110 and/orthe platform 120. As shown in FIG. 2 , the device 200 may include a bus210, a processor 220, a memory 230, a storage component 240, an inputcomponent 250, an output component 260, and a communication interface270.

The bus 210 includes a component that permits communication among thecomponents of the device 200. The processor 220 is implemented inhardware, firmware, or a combination of hardware and software. Theprocessor 220 is a central processing unit (CPU), a graphics processingunit (GPU), an accelerated processing unit (APU), a microprocessor, amicrocontroller, a digital signal processor (DSP), a field-programmablegate array (FPGA), an application-specific integrated circuit (ASIC), oranother type of processing component. In some implementations, theprocessor 220 includes one or more processors capable of beingprogrammed to perform a function. The memory 230 includes a randomaccess memory (RAM), a read only memory (ROM), and/or another type ofdynamic or static storage device (e.g. a flash memory, a magneticmemory, and/or an optical memory) that stores information and/orinstructions for use by the processor 220.

The storage component 240 stores information and/or software related tothe operation and use of the device 200. For example, the storagecomponent 240 may include a hard disk (e.g. a magnetic disk, an opticaldisk, a magneto-optic disk, and/or a solid state disk), a compact disc(CD), a digital versatile disc (DVD), a floppy disk, a cartridge, amagnetic tape, and/or another type of non-transitory computer-readablemedium, along with a corresponding drive.

The input component 250 includes a component that permits the device 200to receive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, the input component 250 mayinclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). The output component 260 includes a component that providesoutput information from the device 200 (e.g. a display, a speaker,and/or one or more light-emitting diodes (LEDs)).

The communication interface 270 includes a transceiver-like component(e.g., a transceiver and/or a separate receiver and transmitter) thatenables the device 200 to communicate with other devices, such as via awired connection, a wireless connection, or a combination of wired andwireless connections. The communication interface 270 may permit thedevice 200 to receive information from another device and/or provideinformation to another device. For example, the communication interface270 may include an Ethernet interface, an optical interface, a coaxialinterface, an infrared interface, a radio frequency (RF) interface, auniversal serial bus (USB) interface, a Wi-Fi interface, a cellularnetwork interface, or the like.

The device 200 may perform one or more processes described herein. Thedevice 200 may perform these processes in response to the processor 220executing software instructions stored by a non-transitorycomputer-readable medium, such as the memory 230 and/or the storagecomponent 240. A computer-readable medium is defined herein as anon-transitory memory device. A memory device includes memory spacewithin a single physical storage device or memory space spread acrossmultiple physical storage devices.

Software instructions may be read into the memory 230 and/or the storagecomponent 240 from another computer-readable medium or from anotherdevice via the communication interface 270. When executed, softwareinstructions stored in the memory 230 and/or the storage component 240may cause the processor 220 to perform one or more processes describedherein. Additionally, or alternatively, hardwired circuitry may be usedin place of or in combination with software instructions to perform oneor more processes described herein. Thus, implementations describedherein are not limited to any specific combination of hardware circuitryand software.

The number and arrangement of components shown in FIG. 2 are provided asan example. In practice, the device 200 may include additionalcomponents, fewer components, different components, or differentlyarranged components than those shown in FIG. 2 . Additionally, oralternatively, a set of components (e.g., one or more components) of thedevice 200 may perform one or more functions described as beingperformed by another set of components of the device 200.

A 5G media streaming (5GMS) system may be an assembly of applicationfunctions, application servers, and interfaces from the 5G mediastreaming architecture that support either downlink media streamingservices or uplink media streaming services, or both. A 5GMS ApplicationProvider may include a party that interacts with functions of the 5GMSsystem and supplies a 5GMS Aware Application that interacts withfunctions of the 5GMS system. The 5GMS Aware Application may refer to anapplication in the user equipment (UE), provided by the 5GMS ApplicationProvider, that contains the service logic of the 5GMS applicationservice, and interacts with other 5GMS Client and Network functions viathe interfaces and application programming interfaces (APIs) defined inthe 5GMS architecture. A 5GMS Client may refer to a UE function that iseither a 5GMS downlink (5GMSd) Client or a 5GMS uplink (5GMSu) Client,or both.

The 5GMSd Client may refer to a UE function that includes at least a 5Gmedia streaming player and a media session handler for downlinkstreaming and that may be accessed through well-defined interfaces/APIs.The 5GMSu Client may refer to an originator of a 5GMSu service that maybe accessed through well-defined interfaces/APIs. A 5GMSu media streamermay refer to a UE function that enables uplink delivery of streamingmedia content to an Application Server (AS) function of the 5GMSApplication Provider, and which interacts with both the 5GMSu AwareApplication for media capture and subsequent streaming, and the MediaSession Handler for media session control.

A dynamic policy may refer to a dynamic policy and charging control(PCC) rule for an uplink or downlink application flow during a mediasession. An egest session may refer to an uplink media streaming sessionfrom the 5GMS AS towards the 5GMSu Application Provider. An ingestsession may refer to a session to upload the media content to a 5GMSdAS. A policy template may refer to a collection of (semi-static) Policyor Control Function (PCF)/Network Exposure Function (NEF) API parameterswhich are specific to the Application Provider and also the resultingPCC rule. A policy template ID may identify the desired policy template,which is used by the 5GMSd Application Function (AF) to select theappropriate PCF/NEF API towards the 5G system so that the PCF cancompile the desired PCC rule. The Media Player Entry may refer to adocument or a pointer to a document that defines a media presentation(e.g., a media presentation description (MPD) for DASH or a uniformresource locator (URL) to a video clip file). A Media Streamer Entry mayrefer to a pointer (e.g., in the form of a URL) that defines an entrypoint of an uplink media streaming session. A presentation entry mayrefer to a document or a pointer to a document that defines anapplication presentation, such as an HTML5 document.

A Provisioning Session may refer to a data structure supplied at aninterface (M1d) by a 5GMSd Application provider that configures the5GMSd features relevant to a set of 5GMSd Aware Applications. A 5GMSdMedia Player may refer to a UE function that enables playback andrendering of a media presentation based on a media play entry andexposing some basic controls such as play, pause, seek, stop, to the5GMSd Aware Application. Server Access Information may refer to a set ofparameters and addresses (including 5GMSd AF and 5GMSd AS addresses)which are needed to activate the reception of a streaming session. AService and Content Discovery may refer to functionality and proceduresprovided by a 5GMSd Application Provider to a 5GMS Aware Applicationthat enables the end user to discover the available streaming serviceand content offerings and select a specific service or content item foraccess. A Service Announcement may refer to procedures conducted betweenthe 5GMS Aware Application and the 5GMS Application Provider such thatthe 5GMS Aware Application is able to obtain 5GMS Service AccessInformation, either directly or in the form of a reference to thatinformation.

A third party player may refer to a part of an application that usesAPIs to exercise selected 5GMSd functions to play back media content. Athird party uplink streamer may refer to a part of an application thatuses APIs to exercise selected 5GMSu functions to capture and streammedia content.

FIG. 3 is a diagram of a media architecture 300 for media streamingaccording to embodiments. A 5GMS Application Provider 301 may use 5GMSfor uplink streaming services or downlink streaming services. 5GMSApplication provider 301 may provide a 5GMS Aware Application 302 on theUE 303 to make use of 5GMS Client 304 and network functions usinginterfaces and defined in 5GMS. The 5GMS Aware Application 302 maycontain the service logic of the 5GMS application service, and mayinteract with other 5GMS client and network functions via the interfacesand APIs defined in the 5GMS architecture. AS 305 may be an AS dedicatedto 5G Media Uplink Streaming. 5GMS Client 304 may be a UE 303 internalfunction dedicated to 5G Media Uplink Streaming.

5GMS AF 306 and 5GMS AS 305 may be Data Network (DN) 307 functions.Functions in trusted DNs may be trusted by the operator's network.Therefore, AFs in trusted DNs may directly communicate with all 5G Corefunctions. Functions in external DNs may only communicate with 5G Corefunctions via the NEF 308 using link 320.

The media architecture 300 may connect UE 303 internal functions andrelated network functions for 5G Media Uplink Streaming. Accordingly,media architecture 300 may include a number of functions. For example,5GMS Client 304 on UE 303 may be an originator of 5GMS service that maybe accessed through interfaces/APIs. 5GMS Client 304 may include twosub-functions, media session handler 309 and media streamer 310. Mediasession handler 309 may communicate with the 5GMS AF 306 in order toestablish, control and support the delivery of a media session. TheMedia Session Handler 309 may expose APIs that can be used by the 5GMSAware Application 302. Media Streamer 310 may communicate with 5GMS AS305 in order to stream the media content and provide a service to the5GMS Aware Application 302 for media capturing and streaming, and theMedia Session Handler 309 for media session control. 5GMS AwareApplication 302 may control 5GMS Client 304 by implementing externalapplication or content service provider specific logic and enabling theestablishment of a media session. 5GMS AS 305 may host 5G mediafunctions and may be implemented as a content delivery network (CDN),for example. 5GMS Application Provider 301 may be an externalapplication or content specific media functionality, e.g., mediastorage, consumption, transcoding and redistribution that uses 5GMS tostream media from 5GMS Aware Application 302. 5GMS AF 306 may providevarious control functions to the Media Session Handler 309 on the UE 303and/or to 5GMS Application Provider 301. 5GMS AF 306 may relay orinitiate a request for different PCF 311 treatment or interact withother network functions. The 5GMS AF 306 may be connected to the PCF 311by an N5 interface 319.

Media architecture 300 may include a number of different interfaces. Forexample, link 321 may relate to M1u, which may be a 5GMS ProvisioningAPI exposed by AF 306 to provision usage of media architecture 300 andto obtain feedback. Link 322 may relate to M2u, which may be a 5GMSPublish API exposed by 5GMS AS 305 and used when 5GMS AS 305 in trustedDN, such as DN 307, is selected to receive content for streamingservice. Link 323 may relate to M3u, which may be an internal API usedto exchange information for content hosting on 5GMS AS 305 within atrusted DN such as DN 307. Link 324 may relate to M4u, which may be aMedia Uplink Streaming API exposed by 5GMS AS 323 to Media Streamer 310to stream media content. Link 325 may relate to M5u, which may be aMedia Session Handling API exposed by 5GMS AF 305 to Media SessionHandler for media session handling, control and assistance that alsoinclude appropriate security mechanisms e.g. authorization andauthentication. Link 326 may relate to M6u, which may be a UE 303 MediaSession Handling API exposed by Media Session Handler 309 to 5GMS AwareApplication 302 to make use of 5GMS functions. Link 327 may relate toM7u, which may be a UE Media Streamer API exposed by Media Streamer 310to 5GMS Aware Application 302 and Media Session Handler 309 to make useof Media Streamer 310. Link 328 may relate to M8u, which may be anApplication API which is used for information exchange between 5GMSAware Application 302 and 5GMS Application Provider 301, for example toprovide service access information to the 5GMS Aware Application 302.The UE 303 may also be implemented in a self-contained manner such thatinterfaces M6u 326 and M7u 327 are not exposed.

FIG. 4 is a diagram of a 5G edge network architecture 400, according toembodiments. Edge Data Network (EDN) 401 is a local Data Network. EdgeApplication Server (EAS) 402 and Edge Enabler Server (EES) 403 arecontained within the EDN 401. Edge Configuration Server (ECS) 404provides configurations related to EES 403, including details of EDN 401hosting EES 403. User Equipment (UE) 405 contains Application Client(AC) 406 and Edge Enabler Client (EEC) 407. EAS 402, EES 403 and ECS 404may interact with the 3GPP Core Network 408.

EES 403 provides supporting functions needed for EAS 402 and EEC 407.Functionalities of EES 403 may include: provisioning of configurationinformation to EEC 407, enabling exchange of application data trafficwith EAS; supporting the functionalities of API invoker and API exposingfunction, for example as specified in 3GPP TS 23.222; interacting with3GPP Core Network 408 for accessing the capabilities of networkfunctions either directly (e.g. via PCF) or indirectly (e.g. via ServiceCapability Exposure Function (SCEF)/NEF/SCEF+NEF); supporting thefunctionalities of application context transfer; supporting externalexposure of 3GPP network and service capabilities to EASs 402 over linkEDGE-3; supporting the functionalities of registration (i.e.,registration, update, and de-registration) for EEC 407 and EAS; andsupporting the functionalities of triggering EAS 402 instantiation ondemand.

EEC 407 provides supporting functions needed for AC. Functionalities ofEEC 407 may include: retrieval and provisioning of configurationinformation to enable the exchange of Application Data Traffic with EAS402; and discovery of EASs 402 available in the EDN 401.

ECS 404 provides supporting functions needed for the EEC 407 to connectwith an EES 403. Functionalities of ECS 404 are: provisioning of Edgeconfiguration information to the EEC 407, for example the informationfor the EEC 407 to connect to the EES 403 (e.g. service area informationapplicable to LADN); and the information for establishing a connectionwith EESs 403 (such as URI); supporting the functionalities ofregistration (i.e., registration, update, and de-registration) for theEES 403; supporting the functionalities of API invoker and API exposingfunction as specified in 3GPP TS 23.222; and interacting with 3GPP CoreNetwork 408 for accessing the capabilities of network functions eitherdirectly (e.g. PCF) or indirectly (e.g. via SCEF/NEF/SCEF+NEF).

AC 406 is the application resident in the UE 405 performing the clientfunction.

EAS 402 is the application server resident in the EDN 401, performingthe server functions. The AC 406 connects to EAS 402 in order to availthe services of the application with the benefits of Edge Computing. Itis possible that the server functions of an application are availableonly as an EAS 402. However, it is also possible that certain serverfunctions are available both at the edge and in the cloud, as an EAS 402and an Application Server resident in the cloud respectively. The serverfunctions offered by an EAS 402 and its cloud Application Servercounterpart may be the same or may differ; if they differ, theApplication Data Traffic exchanged with the AC may also be different.EAS 402 may consume the 3GPP Core Network 408 capabilities in differentways, such as: it may invoke 3GPP Core Network 408 function APIsdirectly, if it is an entity trusted by the 3GPP Core Network 408; itmay invoke 3GPP Core Network 408 capabilities through EES 403; and itmay invoke the 3GPP Core Network 408 capability through the capabilityexposure functions e.g., SCEF or NEF.

Architecture 400 may include a number of different interfaces forenabling edge applications, which may be referred to as referencepoints. For example, link EDGE-1 may be a reference point which enablesinteractions between the EES 403 and the EEC 407. It supports:registration and de-registration of EEC 407 to EES 403; retrieval andprovisioning of EAS 402 configuration information; and discovery of EASs402 available in the EDN 401.

Link EDGE-2 may be a reference point which enables interactions betweenEES 403 and the 3GPP Core Network 408. It supports: access to 3GPP CoreNetwork 408 functions and APIs for retrieval of network capabilityinformation, e.g. via SCEF and NEF APIs as defined in 3GPP TS 23.501,3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or withEES 403 deployed within the MNO trust domain (see 3GPP TS 23.501 clause5.13, 3GPP TS 23.503, 3GPP TS 23.682). Link EDGE-2 may reuse 3GPPreference points or interfaces of EPS or 5GS considering differentdeployment models.

Link EDGE-3 may be a reference point which enables interactions betweenEES 403 and EASs 402. It supports: registration of EASs 402 withavailability information (e.g. time constraints, location constraints);de-registration of EASs 402 from EES 403; discovery of target EAS 402information to support application context transfer; providing access tonetwork capability information (e.g. location information, Quality ofService (QoS) related information); and requesting the setup of a datasession between AC and EAS 402 with a specific QoS.

Link EDGE-4 may be a reference point which enables interactions betweenECS 404 and EEC 407. It supports: provisioning of Edge configurationinformation to the EEC 407.

Link EDGE-5 may be a reference point which enables interactions betweenAC and EEC 407.

Link EDGE-6 may be a reference point which enables interactions betweenECS 404 and EES 403. It supports: registration of EES 403 information toECS 404.

Link EDGE-7 may be a reference point which enables interactions betweenEAS 402 and the 3GPP Core Network 408. It supports: access to 3GPP CoreNetwork 408 functions and APIs for retrieval of network capabilityinformation, e.g. via SCEF and NEF APIs as defined in 3GPP TS 23.501,3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122; or withEAS 402 deployed within the MNO trust domain (see 3GPP TS 23.501 clause5.13, 3GPP TS 23.682). Link EDGE-7 may reuse 3GPP reference points orinterfaces of EPS or 5GS considering different deployment models.

Link EDGE-8 may be a reference point which enables interactions betweenthe ECS 404 and the 3GPP Core Network 408. It supports: a) access to3GPP Core Network 408 functions and APIs for retrieval of networkcapability information, e.g. via SCEF and NEF APIs as defined in 3GPP TS23.501, 3GPP TS 23.502, 3GPP TS 29.522, 3GPP TS 23.682, 3GPP TS 29.122;and with the ECS 404 deployed within the MNO trust domain (see 3GPP TS23.501 clause 5.13, 3GPP TS 23.682). Link EDGE-8 may reuse 3GPPreference points or interfaces of EPS or 5GS considering differentdeployment models.

The AC 406 may send an inquiry to the EES 403 through the EEC 407, todiscover the suitable EASs. In this inquiry, the AC 406 includes EASdiscovery filters that define the desired characteristics of thesuitable EAS. In the response, the EEC 407 provides the AC 406 the listof matching EASs and some of their characteristics. The AC 406 thenselects the best EAS from the list.

FIG. 5 is a diagram of a 5G media streaming architecture 500 with edgeextensions for enabling edge applications, according to embodiments. The5GMS Application Provider 501, 5GMS Aware Application 502, UE 503, 5GMSclient 504, 5GMS AS 505, 5GMS AF 506, DN 507, NEF 508, media sessionhandler 509, media streamer 510, and PCF 511, along with interfaces M1521, M2 522, M3 523, M4 524, M5 525, M6 526, M7 527, M8 528, N5 519 andN33 520 are similar to their counterparts in FIG. 3 and therefore thedetailed description of these components will be omitted.

The architecture 500 includes an EES 550 as part of the 5GMS AF 506, anEAS 522 on the DN 507, an EEC 554 as part of the media session handler509, and an ECS 556. The EEC 554 is connected to the EES 550 by theEdge-1 interface 570. The EAS 552 is connected to the EES 550 by theEdge-3 interface 572. The EEC 554 is connected to the ECS 556 by theEdge-4 interface 274. The EEC 554 is connected to the 5GMS AwareApplication 502 by the Edge-5 interface 576. The ECS 556 is connected tothe EES 550 by the Edge-6 interface 578. Lastly, the Edge-9 interface580 is connected to the EES 550.

In FIG. 5 , the 5GMS Application Provider (AS) requests to 5GMS AF theprovisioning of the session using the M1 interface. Then, through thesame interface, AP requests provisioning of different session featuresincluding server certificate, content preparation, content hostingconfiguration, reporting, consumption reporting, policy, and others.

In FIG. 5 , the 5GMS Application Provider (AS) requests to 5GMS AF theprovisioning of the session using the M1 interface. Then, through thesame interface, AP requests provisioning of different session featuresincluding server certificate, content preparation, content hostingconfiguration, reporting, consumption reporting, policy, and others.

As discussed above, the current 5G Edge architecture defined in 3GPPTS23.558 only defines the discovery of the edge application byApplication clients. The 3GPP TS26.501 only defines the media streamingarchitecture. It recently added the use of TS23.558 edge architecture aspart of the 5GMSA architecture as an extension. However, the actualmethod of provisioning such services is not defined.

Accordingly, embodiments of the present disclosure provide aprovisioning method of new edge servers based on the triggering eventsof the running edge servers.

Aspects of the present disclosure are directed to extending the 5GMS M1interface. Embodiments of the present disclosure enable setting eventsfor an existing EAS servers so that when the EAS profile reaches certainconditions, one or more events are issued. Embodiments of the presentdisclosure enable subscribing and receiving events from another EASserver for activating a new EAS server.

The EAS properties are defined by its profile known as EASProfile in29.558. The EAS profile may change during its operation. Some of thoseservice KPIs are defined as follows.

TABLE 1 Definition of type EASServiceKPI Attribute Data name type PCardinality Description maxReqRate string O 10 . . . 1 Maximum requestrate from the Application Client supported by the EAS. maxRespTimeUinteger O  0 . . . 1 The maximum response time, in the units ofmilliseconds, advertised for the AC's service requests. This includesthe round trip time of the request and response packet, the processingtime at the EAS and time required by EAS to consume any 3GPP corenetwork capabilities. avail string O 10 . . . 1 Advertised percentage oftime the server is available for the AC's use. avlComp string O  0 . . .1 The maximum compute resource available for the AC. avlGraComp string O 0 . . . 1 The maximum graphical compute resource available for the AC.avlMem string O  0 . . . 1 The maximum memory resource available for theAC. avlStrg string O  0 . . . 1 The maximum storage resource availablefor the AC. connBand BitRate O  0 . . . 1 The connection bandwidth inKbit/s advertised for the AC's use.

Embodiments of the present disclosure defines events based on one ormore KPI parameters, including the KPI parameters from Table 1. If oneor more parameters reach a certain value, the 5GMS AS/EAS may generate acorresponding event. That event can be collected using Data collectionAF.

The 5GMS Application Service Provider (AP) may set an event triggercondition when it provisions a new EAS. The event trigger condition canbe carried in the activation trigger parameter. In an embodiment, eventsmay be set by adding a parameter to the EdgeResourcesConfigurationdocument and/or descriptor. In an embodiment, the 5GMS ApplicationService Provider sets an event trigger condition when it provisions anew EAS. The event trigger condition can be carried in the activationtrigger parameter. As an example, a new property and/or parameter knownas “TriggeringEvents” may be added to the EdgeResourcesConfigurationresource as detailed in Table 2 below.

TABLE 2 Definition of EdgeResourcesConfiguration resource Property nameType Cardinality Description edgeResources ResourceId 1 . . . 1 Anidentifier for this ConfigurationId Metrics Reporting Configuration thatis unique within the scope of the enclosing Provisioning Session. edgeEdge 1 . . . 1 Indicates if the management Management Managment of theedge resource Mode Type session is client-driven or applicationprovider- driven. activation Activation 0 . . . 1 Condition to activateedge Trigger Trigger resources for this Type ProvisioningSession.Triggering TriggerEvents 0 . . . 1 Condition for triggering Eventsevents in this provision Session. profile EASProfile 1 . . . 1 The EASprofile used by the 5GMS AF or by the EEC to discover and select one ormore EAS instances to serve media streaming sessions. The format of theEASProfile is defined in table 8.1.5.2.3-1 of TS 29.558. application ACR0 . . . 1 Application Context Context Requirements Relocation toleranceRelocation Type and requirements. Requirements

In the same or another embodiment, the events may be set using the eventprovisioning API (R1).

According to an aspect, a 5GMS Application Provider may set up theconditions for starting a new edge server by the 5GMS AF. TheApplication Provider may set the conditions for generating events in arunning edge server E1 during creation or updating the provisioning ofthe edge server through the M1 interface. The Application Provider mayalso set the activation conditions for activating a new edge server E2during the creation or updating the provisioning of the edge serverthrough the M1 interface. The 5GMS AF may subscribe to the eventsdefined by E1 during its provisioning. When any of the conditions in E1reaches the set limits or any conditions are satisfied, the 5GMS AF/EASmay issue an event. In some embodiments, since the 5GMS AF may besubscribed to the E1 events, it receives the event issued by E1. The5GMS AF may check that the received specific event meets any activationcondition for E2. If that condition is met, the 5GMS AF may activate theE2 server.

FIG. 6 is a flowchart of an example process 600 for event-drivenprovisioning of edge servers in a 5G media streaming network.

At operation 605, during provisioning or updating of a first edgeapplication server, a 5GMS application provider (AP) may set one or moreevent trigger conditions. In some embodiments, the one or more eventtrigger conditions may be based on one or more dynamic parameters of thefirst edge application server. In some embodiments, the one or moreevent trigger conditions may be based on a maximum request rate from anapplication client (AC) supported by the first edge application server.The one or more event trigger conditions may be based on a maximumresponse time advertised for service requests by an application client(AC). In some embodiments, the one or more event trigger conditions maybe based on at least one of a maximum percentage of time available onthe first edge application server for use by an application client (AC),a maximum compute resource available on the first edge applicationserver for use by the AC, a maximum graphical compute resource availableon the first edge application server for use by the AC, a maximum memoryresource available on the first edge application server for use by theAC, a maximum storage resource available on the first edge applicationserver for use by the AC, or a maximum connection bandwidth available onthe first edge application server for use by the AC.

At operation 610, an indicator event associated with the first edgeapplication server, may be determined by a 5GMS Application Function(AF), based on an indicator event associated with the first EAS, that atleast one of the event trigger conditions of the first EAS is satisfied.The determining may include issuing, by the first edge applicationserver, a trigger event indicating that at least one of the one or moreevent trigger conditions of the first edge application server issatisfied, and listening, by the 5GMS AF, for the trigger event of thefirst edge application server.

At operation 615, during the provisioning or updating of a second edgeapplication server, the 5GMS AP may set one or more activatingconditions for activating the second edge application server. In someembodiments, the one or more activating conditions may be set based onadding a triggering events parameter to an edge resources configurationdescriptor. In some embodiments, the one or more activating conditionsmay be set using an event provisioning application programming interface(API).

At operation 620, the 5GMS AP may generate a trigger event in responseto determining that the at least one of the event trigger conditions ofthe first EAS is satisfied.

At operation 625, the 5GMS AP, that the generated trigger event isassociated with at least one of the activating conditions for activatingthe second EAS and/or the second edge application server may beactivated based on a message associated with the generated trigger eventto the EASs in the 5GMS architecture, the message causing activation ofthe second EAS.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 may include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6 . Additionally, or alternatively, two or more of theblocks of process 600 may be performed in parallel.

Further, the proposed methods may be implemented by processing circuitry(e.g., one or more processors or one or more integrated circuits). Inone example, the one or more processors execute a program that is storedin a non-transitory computer-readable medium to perform one or more ofthe proposed methods.

The techniques described above can be implemented as computer softwareusing computer-readable instructions and physically stored in one ormore computer-readable media.

Embodiments of the present disclosure may be used separately or combinedin any order. Further, each of the embodiments (and methods thereof) maybe implemented by processing circuitry (e.g., one or more processors orone or more integrated circuits). In one example, the one or moreprocessors execute a program that is stored in a non-transitorycomputer-readable medium.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations are possible inlight of the above disclosure or may be acquired from practice of theimplementations.

As used herein, the term component is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Even though combinations of features are recited in the claims and/ordisclosed in the specification, these combinations are not intended tolimit the disclosure of possible implementations. In fact, many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. Although each dependent claimlisted below may directly depend on only one claim, the disclosure ofpossible implementations includes each dependent claim in combinationwith every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and may be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and may be used interchangeably with “one ormore.” Where only one item is intended, the term “one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method for event-driven provisioning of edge application servers in a 5G Media Streaming (5GMS) architecture, the method being executed by at least one processor, the method comprising: setting, by a 5GMS application provider (AP), during provisioning or updating of a first edge application server (EAS), one or more event trigger conditions; setting, by the 5GMS AP, during the provisioning or updating of a second EAS, one or more activating conditions for activating the second EAS; issuing, by the first EAS, a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; determining, by a 5GMS Application Function (AF), that the issued trigger event satisfies the one or more activating conditions for activating the second EAS; and activating, by the 5GMS AF, the second EAS in response to determining that the one or more activating conditions for activating the second EAS is satisfied.
 2. The method of claim 1, wherein the one or more activating conditions are set based on adding a triggering events parameter to an edge resources configuration descriptor.
 3. The method of claim 1, wherein the one or more activating conditions are set using an event provisioning application programming interface (API).
 4. The method of claim 1, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria.
 5. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum request rate from an application client (AC) supported by the first EAS.
 6. The method of claim 4, wherein the one or more event trigger conditions are based on a maximum response time advertised for service requests by an application client (AC).
 7. The method of claim 4, wherein the one or more event trigger conditions are based on at least one of a maximum percentage of time available on the first EAS for use by an application client (AC), a maximum compute resource available on the first EAS for use by the AC, a maximum graphical compute resource available on the first EAS for use by the AC, a maximum memory resource available on the first EAS for use by the AC, a maximum storage resource available on the first EAS for use by the AC, or a maximum connection bandwidth available on the first EAS for use by the AC.
 8. The method of claim 1, wherein the one or more activating conditions are included in an activation trigger parameter of an edge resources configuration descriptor.
 9. A device for event-driven provisioning of edge servers in a 5G Media Streaming (5GMS) architecture, the device comprising: at least one memory configured to store program code; and at least one processor configured to read the program code and operate as instructed by the program code, the program code including: first setting code configured to cause the at least one processor to set, by a 5GMS application provider (AP), during provisioning or updating of a first edge application server (EAS), one or more event trigger conditions; second setting code configured to cause the at least one processor to set, by the AP, during the provisioning or updating of a second EAS, one or more activating conditions for activating the second EAS; issuing code configured to cause the at least one processor to issue, by the first EAS, a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied, first determining code configured to cause the at least one processor to determine, by a 5GMS Application Function (AF), that the issued trigger event satisfies the one or more activating conditions for activating the second EAS; and activating determining code configured to cause the at least one processor to activate, by the 5GMS AF, the second EAS in response to determining that the one or more activating conditions for activating the second EAS is satisfied.
 10. The device of claim 9, wherein the one or more activating conditions are set based on adding a triggering events parameter to an edge resources configuration descriptor.
 11. The device of claim 9, wherein the one or more activating conditions are set using an event provisioning application programming interface (API).
 12. The device of claim 9, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria.
 13. The device of claim 12, wherein the one or more event trigger conditions are based on a maximum request rate from an application client (AC) supported by the first EAS.
 14. The device of claim 12, wherein the one or more event trigger conditions are based on a maximum response time advertised for service requests by an application client (AC).
 15. The device of claim 12, wherein the one or more event trigger conditions are based on at least one of a maximum percentage of time available on the first EAS for use by an application client (AC), a maximum compute resource available on the first EAS for use by the AC, a maximum graphical compute resource available on the first EAS for use by the AC, a maximum memory resource available on the first EAS for use by the AC, a maximum storage resource available on the first EAS for use by the AC, or a maximum connection bandwidth available on the first EAS for use by the AC.
 16. The device of claim 12, wherein the one or more activating conditions are included in an activation trigger parameter of an edge resources configuration descriptor.
 17. A non-transitory computer-readable medium storing instructions, the instructions comprising: one or more instructions that, when executed by one or more processors of a device for event-driven provisioning of edge servers in a 5G Media Streaming (5GMS) architecture, cause the one or more processors to: set, by a 5GMS application provider (AP), during provisioning or updating of a first edge application server (EAS), one or more event trigger conditions; set, by the 5GMS AP, during the provisioning or updating of a second EAS, one or more activating conditions for activating the second EAS; issue, by the first EAS, a trigger event indicating that at least one of the one or more event trigger conditions of the first EAS is satisfied; determine, by a 5GMS Application Function (AF), that the issued trigger event satisfies the one or more activating conditions for activating the second EAS; and activate, by the 5GMS AF, the second EAS in response to determining that the one or more activating conditions for activating the second EAS is satisfied.
 18. The non-transitory computer-readable medium of claim 17, wherein the one or more activating conditions are set based on adding a triggering events parameter to an edge resources configuration descriptor.
 19. The non-transitory computer-readable medium of claim 17, wherein the one or more activating conditions are set using an event provisioning application programming interface (API).
 20. The non-transitory computer-readable medium of claim 17, wherein the one or more event trigger conditions are based on one or more dynamic parameters of the first EAS satisfying one or more respective criteria. 